Slicing of network resources for dual connectivity using NR

ABSTRACT

Exemplary embodiments include methods and/or procedures performed by a first network node (1460) in a radio access network, RAN, the first network node (1460) being in communication with a second network node (1460b) configured with a different radio access technology, RAT, than the first network node (1460). Such exemplary embodiments include determining (1210) one or more radio resource management (RRM) identifiers associated with at least one of the following: a user equipment, UE, served by the first network node; a subscriber associated with the UE; and a group of UEs served by the first network node. Exemplary embodiments also include esending (1220) a request for the second network node to establish dual connectivity, as a secondary node, SN, with the UE, wherein the request comprises information relating to the one or more RRM identifiers. Some embodiments can include managing (1230) the UE&#39;s access to resources provided by the RAN based on one or more policies associated with the one or more RRM identifiers, while the information relating to the one or more RRM identifiers can map to one or more further policies for managing UE access to resources provided by a RAN including the second network node.

TECHNICAL FIELD

The present application relates generally to the field of wirelesscommunication networks, and more specifically to dual-connectivitybetween a user equipment and a wireless communication network using twodifferent types of radio access technologies (RATs).

BACKGROUND

Multi-connectivity (also referred to as “Dual-Connectivity” or “DC”) canbe envisioned as an important feature for fifth-generation (5G) RANarchitectures standardized by 3GPP. FIG. 1 illustrates a high-level viewof the 5G network architecture, consisting of a Next Generation RAN(NG-RAN) and a 5G Core (5GC). The NG-RAN can comprise a set ofnext-generation Node B's (gNBs) connected to the 5GC via one or more NGinterfaces, whereas the gNBs can be connected to each other via one ormore Xn interfaces. Each of the gNBs can support frequency divisionduplexing (FDD), time division duplexing (TDD), or a combinationthereof.

The NG RAN logical nodes shown in FIG. 1 (and described in TR38.801v1.2.0) include a Central Unit (CU or gNB-CU) and one or moreDistributed Units (DU or gNB-DU). CU is a logical node that is acentralized unit that hosts high layer protocols and includes a numberof gNB functions, including controlling the operation of DUs. A DU is adecentralized logical node that hosts lower layer protocols and caninclude, depending on the functional split option, various subsets ofthe gNB functions. (As used herein, the terms “central unit” and“centralized unit” are used interchangeably, and the terms “distributedunit” and “decentralized unit” are used interchangeability.)

The NG, Xn-C and F1 items shown in FIG. 1 are logical interfaces. ForNG-RAN, the NG and Xn-C interfaces for a split gNB (e.g., consisting ofa gNB-CU and gNB-DUs) terminate in the gNB-CU. Likewise, for EN-DC, theS1-U and X2-C interfaces for a split gNB terminate in the gNB-CU. ThegNB-CU connects to gNB-DUs over respective F1 logical interfaces. ThegNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GCas a gNB, e.g., the F1 interface is not visible beyond gNB-CU.

Furthermore, the F1 interface between the gNB-CU and gNB-DU isspecified, or based on, the following general principles:

-   -   F1 is an open interface;    -   F1 supports the exchange of signalling information between        respective endpoints, as well as data transmission to the        respective endpoints;    -   from a logical standpoint, F1 is a point-to-point interface        between the endpoints (even in the absence of a physical direct        connection between the endpoints);    -   F1 supports control plane (CP) and user plane (UP) separation,        such that a gNB-CU may be separated in CP and UP;    -   F1 separates Radio Network Layer (RNL) and Transport Network        Layer (TNL);    -   F1 enables exchange of user-equipment (UE) associated        information and non-UE associated information;    -   F1 is defined to be future proof with respect to new        requirements, services, and functions;    -   A gNB terminates X2, Xn, NG and S1-U interfaces.

Furthermore, a CU can host protocols and/or layers such as RadioResource Control (RRC), Service Data Adaptation Protocol (SDAP), andPacket Data Convergence Protocol (PDCP), while a DU can host protocolsand/or layers such as Radio Link Control (RLC), Medium Access Control(MAC), and physical layer (PHY). Other variants of protocoldistributions between CU and DU exist, such as hosting the RRC, PDCP andpart of the RLC protocol in CU (e.g., Automatic Retransmission Request(ARQ) function), while hosting the remaining parts of the RLC protocolin the DU, together with MAC and PHY. In some exemplary embodiments, CUcan host RRC and PDCP, where PDCP can handle both UP traffic and CPtraffic. Nevertheless, other exemplary embodiments may utilize otherprotocol splits that by hosting certain protocols in CU and certainothers in the DU. Exemplary embodiments can also locate centralizedcontrol plane protocols (e.g., PDCP-C and RRC) in a different CU withrespect to the centralized user plane protocols (e.g., PDCP-U).

3GPP RAN WG3 has also stared working on a new open interface—referred toas “E1”—between the control plane (CU-CP) and the user plane (CU-UP)parts of CU. The related agreements are collected in TR 38.830 anddiscussed further below.

In the architecture identified by CUs and DUs, DC can be achieved bymeans of allowing a UE to connect to multiple DUs served by the same CUor by allowing a UE to connect to multiple DUs served by different CUs.As illustrated in FIG. 1, a gNB can include a gNB-CU connected to one ormore gNB-DUs via respective F1 interfaces, all of which are describedhereinafter in greater detail. In the NG-RAN architecture, however, agNB-DU can be connected to only a single gNB-CU.

The NG-RAN is layered into a Radio Network Layer (RNL) and a TransportNetwork Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logicalnodes and interfaces between them, is defined as part of the RNL. Foreach NG-RAN interface (NG, Xn, F1) the related TNL protocol and thefunctionality are specified. The TNL provides services for user planetransport and signaling transport. In some exemplary configurations,each gNB can be connected to all 5GC nodes within a “pool area,” asdefined in 3GPP TS 23.501. If security protection for control plane anduser plane data on TNL of NG-RAN interfaces has to be supported, NDS/IP(3GPP TS 33.401) shall be applied. Furthermore, in some exemplaryconfiguration, each gNB can be connected to all Access and MobilityManagement Functions (AMFs) within an AMF Region. The AMF Region isdefined in 3GPP TS 23.501 as consisting of one or more AMF Sets, eachAMF Set consisting of some AMFs that serve a given area and NetworkSlice, which is defined generically in 23.501 as a logical network thatprovides specific capabilities and characteristics.

As mentioned above, multi-connectivity (e.g., dual-connectivity or “DC”)is envisioned as an important feature to be supported in RAN 5Garchitectures. In this context, DC support includes establishing masternode (MN) and secondary nodes (SNs) and distributing UP traffic to theMN and SNs according to optimal, preferred, and/or desirable traffic andradio resource management techniques. CP traffic is assumed to terminatein one node only, i.e. the MN.

FIGS. 2 and 3 show the protocol and interfaces involved in DC, asdescribed in 3GPP TS 38.300 v0.6.0. FIG. 2 illustrates that a Master gNB(MgNB) can provide a Master Cell Group (MCG) bearer and a MCG splitbearer, whereby the MgNB can forward PDCP bearer traffic to a SecondarygNB (SgNB) via Xn. In addition to PDCP, each of the bearer types canutilize various other protocols mentioned above. FIG. 3 illustrates thatthe SgNB can provide a Secondary Cell Group (SCG) bearer and an SCGsplit bearer, whereby the SgNB can forward PDCP bearer traffic to theMgNB via Xn. In addition to PDCP, each of the bearer types can utilizevarious other protocols mentioned above. In some exemplary embodiments,the MgNB and/or SgNB can utilize the RAN split architecture (e.g., CUand DU) discussed above.

Furthermore, dual connectivity using multiple radio access technologies(multi-RAT DC or MR-DC, for short) is envisioned as an important featurein 5G RAN architectures to deliver enhanced end-user bit rate. In MR-DC,both Long-Term Evolution (LTE, also known as “4G”) and NR RATsconcurrently provide radio resources toward the UE. When MR-DC isapplied, the MN can anchor the control plane (CP) towards the CN, whilethe SN can provide control and user plane resources to the UE viacoordination with the MN. FIG. 4 (from 3GPP TS 37.340) shows anexemplary CP protocol architecture for MR-DC, in which the UE receivesRRC messages from both MN and SN but only adopts an RRC state based onthe MN. Within the MR-DC user plane (UP), various bearer types areavailable. FIG. 5 (also from TS 37.340) shows an exemplary MR-DC UPprotocol architecture including an exemplary MCG bearer, MCG splitbearer, SCG bearer, and SCG split bearer. The split-bearer communicationoccurs via the Xn interface, and each of the bearer types shown canutilize various protocols mentioned above.

Although the figures and discussion above are in the context of 5G,NG-RAN nodes can provide both NR access via gNB functionality andE-UTRA/LTE access via evolved Node B (eNB) functionality. Many featuresfor connectivity, mobility, support of QoS, etc. apply for both NR/5Gand E-UTRA/LTE access. As such, any feature described for gNBs can alsoapply to eNBs, which are often referred to in this context as “ng-eNB.”For example, it is anticipated that higher/lower layer split describedabove for gNBs will also be used for ng-eNBs.

Furthermore, in the context of 5G/NR, a connectivity option (identifiedin 38.301 as “option 3”) is specified to support DC between a nodeproviding E-UTRA resources (e.g., LTE eNB) and a node providing NRresources (e.g., gNB). This connectivity option can also be referred toas E-UTRAN-NR Dual Connectivity (or EN-DC for short). In thisarrangement, an LTE eNB acts as MN (CP anchor) and the NR gNB acts as SN(providing additional UP resources). FIGS. 6 and 7 show exemplarycontrol plane (CP) and user plane (UP) connectivity, respectively,between the LTE MN, the NR SN, and the EPC. As illustrated in FIGS. 6and 7, EN-DC supports CP connectivity from RAN nodes towards the EPC(e.g., MME) via the S1 interface, and UP connectivity from the eNB/gNBtowards the EPC via the S1-U interface. The interface between eNB andgNB can be an X2 interface.

Alternately, when the 5G Core Network (5GC, alternately referred to asNGC) serves the UE, an LTE eNB and an NR gNB can be connected via an Xninterface, which can comprise Xn-U and Xn-C portions for UP and CP,respectively. One of the features of Rel-15 LTE (also referred to as“eLTE”) is that eNBs can connect to the 5GC via the NG interface, whichcan comprise NG-U and NG-C portions for UP and CP, respectively. VariousDC options between the eNB and gNB are also available in thisarchitecture, such that the MN can be either the eNB or the gNB. FIG. 8illustrates exemplary MR-DC connectivity with the NGC and an eLTE eNBMN, referred to as “option 7” in 3GPP TR 38.801 In this arrangement, SNUP traffic flows to the NGC either directly (as shown on right) or viathe MN (as shown on left).

“Slicing” is a central concept in 5G networks with new mechanismsintroduced in 5GC and “slicing” mechanisms also available in 4G EPC.Although “Network Slicing” is defined generically in 23.501, discussedabove, the term “slicing” is used herein to refer to techniques thatminimize impact between groups of users that are sharing a pool ofnetwork resources (e.g., radio resources), based on policies for howmany resources can be consumed by each group of users during overloadconditions on the network resources. Exemplary radio resource managementpolicies for groups include limiting the amount of resources consumed byinbound roaming usings in a congested cell, and controlling theproportion of resources available for public safety users versusconsumer (e.g., Mobile Broadband) users.

Even so, there are various problems, drawbacks, and/or issues related toidentifying groups of users that can prevent and/or inhibit thedeployment of EN-DC for networks that employ slicing.

SUMMARY

Accordingly, exemplary embodiments of the present disclosure addressthese shortcomings in dual-connectivity (DC) implementations in mixed NRand LTE networks, thereby facilitating group-level radio resourcemanagement for both RATs and/or RANs. Such exemplary embodiments caninclude methods and/or procedures performed by a first network node(e.g., eNB or gNB) in a RAN (e.g., LTE/E-UTRAN or NR/NG-RAN). The firstnetwork node can be in communication with a second network node (e.g.,gNB or eNB) having a different radio access technology (RAT) than thefirst network node.

The exemplary methods and/or procedures can include determining one ormore radio resource management (RRM) identifiers associated with atleast one of: a user equipment (UE) served by the first network node; asubscriber associated with the UE; and a group of UEs served by thefirst network node. In some embodiments, determining the RRM identifierscan include receiving the RRM identifiers from a core network.

The exemplary methods and/or procedures can also include sending arequest for the second network node to establish dual connectivity, as asecondary node (SN), with the UE, wherein the request comprisesinformation relating to the one or more group identifiers. In someembodiments, the exemplary methods and/or procedures can also includemanaging the UE's access to resources of the RAN based on the one ormore group identifiers. In some embodiments, the first network node canmanage the UE's access to resources of the RAN further based on aprofile of the subscriber associated with the UE. In some embodiments,the information relating to the one or more RRM identifiers can map toone or more further policies for managing UE access to resourcesprovided by a RAN that includes the second network node. In someembodiments, the one or more policies can be the same as the one or morefurther policies.

Other exemplary embodiments can include methods and/or proceduresperformed by a second network node (e.g., gNB or eNB) in a RAN (e.g.,NR/NG-RAN or LTE/E-UTRAN). The second network node can be incommunication with a first network node (e.g., eNB or gNB) having adifferent RAT than the second network node. The exemplary methods and/orprocedures can include receiving a request from a first network node toestablish dual connectivity, as a secondary node (SN), with a userequipment (UE) served by the first network node, wherein the requestcomprises information relating to one or more Radio Resource Management(RRM) identifiers that are associated with at least one of: a userequipment (UE) served by the first network node; a subscriber associatedwith the UE; and a group of UEs served by the first network node.

The exemplary methods and/or procedures can also mapping the informationrelating to the one or more RRM identifiers to one or more policies formanaging the UE's access to resources provided by the second networknode. The exemplary method and/or procedure can also include managingthe UE's access to the resources in accordance with the one or morepolicies. In some embodiments, the one or more RRM identifiers can mapto one or more further policies for managing UE access to resourcesprovided by a RAN that includes the first network node. In someembodiments, the one or more policies can be the same as the one or morefurther policies.

Other exemplary embodiments can also include network nodes (e.g., eNBs,gNBs, base stations, etc., or components thereof such as gNB-CU and/orgNB-DU) configured to perform operations corresponding to the exemplarymethods and/or procedures. Other exemplary embodiments can also includenon-transitory, computer-readable media storing computer-executableinstructions that, when executed by a processing unit of a network node,configure the network node to perform the operations corresponding tothe exemplary methods and/or procedures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a high-level view of the 5G network architecture,consisting of a Next Generation RAN (NG-RAN) and a 5G Core (5GC).

FIGS. 2 and 3 show exemplary protocols and interfaces utilized in dualconnectivity (DC) involving a master gNB (MgNB) and a secondary gNB(SgNB).

FIG. 4 shows an exemplary control-plane (CP) protocol architecture for5G multi-RAT DC.

FIG. 5 shows an exemplary user-plane (UP) protocol architecture for 5Gmulti-RAT DC.

FIGS. 6 and 7 show exemplary CP and UP connectivity, respectively, in aMR-DC scenario involving a master eNB, a secondary gNB, and an EvolvedPacket Core (EPC) network.

FIG. 8 shows exemplary CP and UP connectivity in a MR-DC scenarioinvolving a master eNB, a secondary gNB, and a 5GC (NGC) network.

FIG. 9 illustrates examples of how different “slices” of an LTE RAN(e.g., E-UTRAN) can be identified based on various identifiers.

FIG. 10 further illustrates how these various identifiers can be appliedto RAN resource scheduling according to particular policies.

FIG. 11, comprising FIGS. 11A and 11B, shows an exemplary format of anSgNB Addition Request message, according to some exemplary embodimentsof the present disclosure.

FIG. 12 shows an exemplary method and/or procedure performed by a firstnetwork node (e.g., eNB) in a radio access network (RAN, e.g., E-UTRAN),according to various exemplary embodiments of the present disclosure.

FIG. 13 shows an exemplary method and/or procedure performed by a secondnetwork node (e.g., gNB) in a RAN (e.g., NG-RAN), according to variousexemplary embodiments of the present disclosure.

FIG. 14 is a block diagram of an exemplary wireless network configurableaccording to various exemplary embodiments of the present disclosure.

FIG. 15 is a block diagram of an exemplary user equipment (UE)configurable according to various exemplary embodiments of the presentdisclosure.

FIG. 16 is a block diagram of illustrating a virtualization environmentthat can facilitate virtualization of various functions implementedaccording to various exemplary embodiments of the present disclosure.

FIGS. 17-18 are block diagrams of exemplary communication systemsconfigurable according to various exemplary embodiments of the presentdisclosure.

FIG. 19-22 are flow diagrams illustrating various exemplary methodsand/or procedures implemented in a communication system, according tovarious exemplary embodiments of the present disclosure.

DETAILED DESCRIPTION

Exemplary embodiments briefly summarized above will now be describedmore fully with reference to the accompanying drawings. Thesedescriptions are provided by way of example to explain the subjectmatter to those skilled in the art, and should not be construed aslimiting the scope of the subject matter to only the embodimentsdescribed herein. More specifically, examples are provided below thatillustrate the operation of various embodiments according to theadvantages discussed above.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsand/or procedures disclosed herein do not have to be performed in theexact order disclosed, unless a step is explicitly described asfollowing or preceding another step and/or where it is implicit that astep must follow or precede another step. Any feature of any of theembodiments disclosed herein can be applied to any other embodiment,wherever appropriate. Likewise, any advantage of any of the embodimentscan apply to any other embodiments, and vice versa. Other objectives,features and advantages of the disclosed embodiments will be apparentfrom the following description.

Exemplary embodiments of the present disclosure are described in termsof an LTE eNB in the role of MN and an NR gNB in the role of SN.Nevertheless, this is merely for the purposes of illustrating features,benefits, and/or underlying principles. As such, a person skilled in theart will readily comprehend that the features, benefits, and/orprinciples apply equally to other embodiments in which a gNB is MN andthe SN is an eNB or another gNB. Furthermore, such features, benefits,and/or principles can also apply to when the SN is a node in a non-3GPPradio access network (RAN).

Furthermore, although the descriptions below are given in terms ofspecific group identifiers (e.g., SPID), these are merely exemplary andother group identifiers can be utilized in the same or substantiallysimilar manner. Moreover, information related to, or representing, suchgroup identifiers can also be communicated instead of thespecifically-mentioned group identifiers. For example, rather thancommunicating an SPID from MN to SN, such information may be conveyed asan RFSP when the SN is connected to the 5GC.

As mentioned above, there are various problems, drawbacks, and/or issuesrelated to identifying groups of users that can prevent and/or inhibitthe deployment of EN-DC for networks that employ slicing. These arediscussed in more detail below.

Policies for “slicing” in LTE (e.g., E-UTRAN and EPC) can be based onone or a combination of the following identifiers related to user,groups, and/or networks:

-   -   Public Land Mobile Network ID (PLMN-id) (e.g., “network        sharing”);    -   Quality of Service (QoS) Class Identifier (QCI);    -   Subscribers Profile ID for RAT/Frequency Priority (SPID) (e.g.,        inbound roamers are assigned a certain SPID);    -   Dedicated Core Network ID (DCN-id) (e.g., users belonging to the        public safety DCN shall be treated according to a certain        policy);    -   MME Group Identity (MMEGI); and/or    -   Membership of a Closed Subscriber Group (CSG).        In LTE, all identifiers and information received from the EPC        are available to the eNB, and can be used for network resource        management (“slicing”) between groups of users. FIG. 9        illustrates examples of how different “slices” of a RAN (e.g.,        E-UTRAN) can be identified based on various identifiers,        including the ones mentioned above. More specifically, two        public land mobile networks (PLMNs) X and Y utilize four        different slices of a shared RAN. PLMN X utilizes RAN slice 1,        which two core network (CN) instances in PLMN Y utilize RAN        slices 2-4. The RAN slice definition/configuration table shows        various exemplary identifiers associated with each of these RAN        slices. FIG. 10 further illustrates how the four RAN slices        shown in FIG. 9 can be associated with various scheduling        parameters (e.g., via a flexible QoS feature table) that can be        applied to RAN resource scheduling according to particular radio        resource policies (RRP) and RAN resource partitioning shares.

It is expected that initial 5G deployments will use EN-DC, with LTE eNBas MN (e.g., MeNB) and with an interface to the 4G EPC. In such case, aNR gNB is SN (e.g., SgNB) and, as such, receives requests to establishresources over X2 from the MeNB. A general principle is that LTEresources are managed by the MeNB, while the SgNB has a large degree ofautonomy in managing NR resources. Nevertheless, although there are manypossible identifiers could be used as basis for group-level radioresource management according to a policy (“slicing”) in EN-DC, the MN(e.g., MeNB) only sends a subset of these identifiers to the SN (e.g.,SgNB), in particular the UE PLMN-id and QCI per bearer. For example, theUE's SPID and DCN-id are not available over the X2 (or Xn) interface. Assuch, this lack of information prevents the NR RAN (e.g., gNB) fromcontrolling network resources according the same range of policiesavailable to the LTE RAN (e.g., eNB). In short, the possibilities forslicing of NR resources are limited compared to what is possible forLTE.

In some exemplary embodiments, when the MN (e.g., MeNB) has received ordetermined an SPID group identifier from the EPC, it forwards it in anSN Setup Request (e.g. X2: SgNB Addition Request message) to the SN(e.g., SgNB). In some exemplary embodiments, when the MN has received ordetermined a valid DCN-id group identifier for the UE, it forwards it inthe SN Setup Request to the SN. In some embodiments, both SPID andDCN-id can be sent in the same SN Setup Request message.

In other exemplary embodiments, the MN can perform anoperator-configurable mapping of a group identifier to other informationrelating to the group identifier (e.g., a new parameter). For example,the MN can map the DCN-id to a “DCN resource index” and send this to theSN. Such a mapping can serve the purpose of abstracting informationabout the CN connected to the MN, so as not to expose such informationto the SN. Rather, mapping the DCN-id to an index can facilitateproviding the SN with only the information needed to understand theindex values and how they map to a specific policy for the UE.

When the SgNB receives a SN setup request with SPID and/or a DCN-relatedparameter, it can use this for management of NR resources according toan operator-configured policy. As an example, if the SPID and or DCN-IDidentify a policy for which a predefined pool of resources can be usedby the UE, the SN can enable such policy and, e.g., prioritize the UE'saccess to resources of the NR RAN, over access by other UEs that are notassociated by the identified policy (e.g., not identified by the SPIDand/or DCN-id and/or related parameters).

More generally, the SN can use any combination of SPID, DCN-relatedinformation, PLMN-id, QCI, CSG membership, etc. to define groups ofusers and/or an appropriate resource management policy that relates tothe UE's active services and/or services identified with the profile ofa subscriber associated with the UE. For example, in the context of NRresource scheduling (e.g., in an NR scheduler), the SN can guaranteethat a particular group of users—defined in any of the ways describedabove—can access a predefined proportion of resources (e.g., radioresources) that can be allocated by the SN. In other words, when thereis no congestion in the NR RAN, resources can be assigned to any userregardless of this policy. On the other hand, when congestion occurs inthe NR RAN, the defined group of users can receive, upon request, thepredetermined proportion of resources in the NR RAN. In other words, thedefined group of users is prioritized over other users who are notincluded in the defined group.

In other exemplary embodiments, the SN can also use policies per groupof users for other NR resource management tasks. For example, the NR RANallocates frequency-domain resources based on division into multiplebandwidth parts (BWPs) that cover the available frequency spectrum.Accordingly, the SN can prioritize access to the various BWPs and/orfrequency ranges within the various BWPs based on membership in thedefined groups.

Various group information for a particular UE can be sent from the MN tothe SN in various ways. In one exemplary embodiment, SPID informationcan be encoded in an SgNB Addition Request message sent by the MN (e.g.,MeNB) to request the preparation of resources for EN-DC operation for aspecific UE. FIG. 11, comprising FIGS. 11A and 11B, shows an exemplaryformat of an SgNB Addition Request message, according to some exemplaryembodiments of the present disclosure. In other exemplary embodiments,other messages such as SgNB Modification Request can be used to carryvarious types of group information for a particular UE.

In other exemplary embodiments, the SN can be arranged in a splitconfiguration comprising a Central Unit (CU) hosting higher layers suchas RRC/PDCP and a Distributed Unit (DU) hosting lower layers such asRLC/MAC/PHY, as described briefly above. For example, the SN can bearranged as a gNB-CU and a gNB-DU. In such embodiments, after receivinginformation relating to one or more group identifier (e.g., SPID, RFSP,DCN-id, etc.) from the MN over an Xn interface, the gNB-CU can forwardall, or a portion of, the received information to the gNB-DU over the F1interface. Such information can be useful for group-based radio resourcemanagement (RRM) policies that are implemented by, or involve, ascheduler functionality resident in the gNB-DU. Exemplary F1 messagesthat could be suitable for providing such information include: UEContext Setup Request, UE Context Modification Request, and DL RRCMessage Transfer. Although described in terms of NR split architecture,such embodiments can also be utilized in LTE split architectures, inwhich an eNB SN (e.g., SeNB) is divided into an eNB-CU and an eNB-DU.Messages appropriate for the eNB-CU/eNB-DU interface can be employed ina similar manner as described above for NR split architectures.

These and other exemplary embodiments can provide various advantagesrelated to radio resource management in dual connectivity scenarios thatare expected to be important for deployment of NR networks. Morespecifically, such embodiments facilitate “slicing” of radio resourcesin dual-connectivity scenarios in which a master node (MN) deploying afirst RAT (e.g., LTe) and a secondary node (SN) deploying a differentsecond RAT (e.g., NR). The MN and the SN can be part of different RANs,or different portions of a single RAN that deploys two different RATs.

By providing group-related identifiers associated with a UE wheninitiating dual-connectivity with the SN, such embodiments facilitate atleast the same degree of “slicing” in the RAN (or portion) including thesecond network node as in the RAN (or portion) including the firstnetwork node. This can facilitate the deployment of 5G/NR networks toprovide additional data capacity to legacy LTE networks viadual-connectivity techniques. These and other advantages and/or benefitscan facilitate more timely design, implementation, and deployment of5G/NR solutions. Furthermore, these and other advantages and/or benefitscan lead to improvements in capacity, throughput, latency, etc. that areenvisioned by 5G/NR and are important for the growth of over-the-top(OTT) data applications or services external to the 5G network.Moreover, these and other advantages and/or benefits can also lead toimproved user experience associated with OTT data applications orservices, particularly with respect to service mobility within the 5Gnetwork.

FIG. 12 illustrates an exemplary method and/or procedure performed by afirst network node (e.g., eNB) in a radio access network (RAN), inaccordance with various exemplary embodiments of the present disclosure.The first network node can be in communication with a second networknode (e.g., gNB) having a different radio access technology (RAT) thanthe first network node. Although the exemplary method and/or procedureis illustrated in FIG. 12 by blocks in a particular order, this order isexemplary and the operations corresponding to the blocks can beperformed in different orders, and can be combined and/or divided intoblocks having different functionality than shown in FIG. 12.Furthermore, exemplary method and/or procedure shown in FIG. 12 can becomplimentary to exemplary method and/or procedure illustrated in FIG.13 below. In other words, exemplary methods and/or procedures shown inFIGS. 12 and 13 are capable of being used cooperatively to provide thebenefits, advantages, and/or solutions to problems describedhereinabove. Optional operations are indicated by dashed lines.

The exemplary method and/or procedure can include the operations ofblock 1210, where the first network node can determine one or more radioresource management (RRM) identifiers associated with at least one of: auser equipment (UE) served by the first network node; a subscriberassociated with the UE; and a group of UEs served by the first networknode. In some embodiments, the operations of block 1210 can include theoperations of block 1212, where the first network node can receive theone or more RRM identifiers from a core network (e.g., a 5GC or an EPC).

The exemplary method and/or procedure can also include the operations ofblock 1220, where the first network node can send a request for thesecond network node to establish dual connectivity, as a secondary node(SN), with the UE, wherein the request comprises information relating tothe one or more RRM identifiers. In some embodiments, the exemplarymethod and/or procedure can also include the operations of block 1230,where the first network node can manage the UE's access to resources ofthe RAN based on the one or more RRM identifiers. In some embodiments,the first network node can manage the UE's access to resources of theRAN further based on a profile of the subscriber associated with the UE.In some embodiments, the information relating to the one or more RRMidentifiers can map to one or more further policies for managing UEaccess to resources provided by a RAN that includes the second networknode. In some embodiments, the one or more policies can be the same asthe one or more further policies.

In some embodiments, each of the one or more RRM identifiers can berelated to one or more of the following: Subscribers Profile ID forRAT/Frequency Priority (SPID), Dedicated Core Network ID (DCN-id),Public Land Mobile Network ID (PLMN-id), Mobility Management Entitygroup identity (MMEGI), QoS Class Indicator (QCI), and Closed SubscriberGroup (CSG) membership.

In some embodiments, the first network node can be an eNB configuredwith an LTE RAT, and the second network node can be a gNB configuredwith an NR RAT. In other embodiments, the second network node can be aneNB configured with an LTE RAT, and the first network node can be a gNBconfigured with an NR RAT.

In some embodiments, the one or more RRM identifiers can include aSubscriber Profile ID for RAT/Frequency Priority (SPID), and theinformation relating to the one or more RRM identifiers can include theSPID. In some embodiments, the one or more RRM identifiers can include aRAT/Frequency Selection Priority (RFSP), and the information relating tothe one or more RRM identifiers can include the RFSP. In someembodiments, the one or more RRM identifiers can include an SPID, andthe information relating to the one or more RRM identifiers can includea RFSP index.

In some embodiments, the one or more RRM identifiers can include aDedicated Core Network ID (DCN-id) and/or a Mobility Management Entitygroup identity (MMEGI). In such embodiments, the information relating tothe one or more group identifiers can include an index value that mapsto one or more policies for managing UE access to resources of a RANthat includes the second network node.

FIG. 13 illustrates an exemplary method and/or procedure performed by asecond network node (e.g., gNB) in a radio access network (RAN), inaccordance with various exemplary embodiments of the present disclosure.The second network node can be in communication with a first networknode (e.g., eNB) having a different radio access technology (RAT) thanthe second network node. Although the exemplary method and/or procedureis illustrated in FIG. 13 by blocks in a particular order, this order isexemplary and the operations corresponding to the blocks can beperformed in different orders, and can be combined and/or divided intoblocks having different functionality than shown in FIG. 13.Furthermore, exemplary method and/or procedure shown in FIG. 13 can becomplimentary to exemplary method and/or procedure illustrated in FIG.12 above. In other words, exemplary methods and/or procedures shown inFIGS. 12 and 13 are capable of being used cooperatively to provide thebenefits, advantages, and/or solutions to problems describedhereinabove. Optional operations are indicated by dashed lines.

The exemplary method and/or procedure can include the operations ofblock 1310, where the second network node can receive a request from afirst network node to establish dual connectivity, as a secondary node(SN), with a user equipment (UE) served by the first network node,wherein the request comprises information relating to one or more RadioResource Management (RRM) identifiers that are associated with at leastone of: a user equipment (UE) served by the first network node; asubscriber associated with the UE; and a group of UEs served by thefirst network node. The exemplary method and/or procedure can alsoinclude the operations of block 1320, where the second network node maymap the information relating to the one or more RRM identifiers to oneor more policies for managing the UE's access to resources provided bythe second network node. In some embodiments, the one or more RRMidentifiers can map to one or more further policies for managing UEaccess to resources provided by a RAN that includes the first networknode. In some embodiments, the one or more policies can be the same asthe one or more further policies.

The exemplary method and/or procedure can include the operations ofblock 1330, where the second network node can manage the UE's access tothe resources in accordance with the one or more policies. In someembodiments, the second network node can manage the UE's access to theresources further based on a profile of the subscriber associated withthe UE. In some embodiments, at least one of the policies can prioritizeaccess by UEs associated with the one or more RRM identifiers overaccess by UEs that are not associated with all of the one or moreidentifiers. In some embodiments, such a policy can prioritize access byUEs associated with the one or more group identifiers to particularbandwidth part (BWP) frequency resources that are allocated by thesecond network node. In some embodiments, at least one of the policiescan guarantee that UEs associated with the one or more RRM identifierscan access at least a predefined proportion of resources available fromthe RAN.

In some embodiments, each of the one or more RRM identifiers can berelated to one or more of the following: Subscribers Profile ID forRAT/Frequency Priority (SPID), Dedicated Core Network ID (DCN-id),Public Land Mobile Network ID (PLMN-id), Mobility Management Entitygroup identity (MMEGI), QoS Class Indicator (QCI), and Closed SubscriberGroup (CSG) membership.

In other embodiments, the second network node can be an eNB configuredwith an LTE RAT, and the first network node can be a gNB configured withan NR RAT. In other embodiments, the first network node can be an eNBconfigured with an LTE RAT, and the second network node can be a gNBconfigured with an NR RAT. In such embodiments, the gNB second networknode can comprise a central unit (CU) and one or more distributed units(DUs). In such embodiments, the request can be received (inblock/operation 1310) by the CU, and the exemplary method and/orprocedure can also include sending (in block/operation 1340) at leastone of the following to at least one DU: the information relating to theone or more RRM identifiers; and the one or more policies. Thisinformation can be sent, e.g., via an F1 interface between the DU(s) andCU.

In some embodiments, if the information relating to the one or moreidentifiers is sent to the DU(s), the operation of block 1340 can bepart of block 1320. In some embodiments, if the one or more policies aresent to the DU(s), the operation of block 1340 can be part of block1330. Other combinations and/or arrangements are also possible.

In some embodiments, the one or more RRM identifiers can include aSubscriber Profile ID for RAT/Frequency Priority (SPID), and theinformation relating to the one or more RRM identifiers can include theSPID. In some embodiments, the one or more RRM identifiers can include aRAT/Frequency Selection Priority (RFSP), and the information relating tothe one or more RRM identifiers can include the RFSP. In someembodiments, the one or more RRM identifiers can include an SPID, andthe information relating to the one or more RRM identifiers can includea RFSP index.

In some embodiments, the one or more RRM identifiers can include aDedicated Core Network ID (DCN-id) and/or a Mobility Management Entitygroup identity (MMEGI). In such embodiments, the information relating tothe one or more group identifiers can include an index value that mapsto one or more policies for managing UE access to resources of a RANthat includes the second network node.

Although the subject matter described herein can be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 14.For simplicity, the wireless network of FIG. 14 only depicts network1430, network nodes 1460 and 1460 b, and WDs 1410, 1410 b, and 1410 c.In practice, a wireless network can further include any additionalelements suitable to support communication between wireless devices orbetween a wireless device and another communication device, such as alandline telephone, a service provider, or any other network node or enddevice. Of the illustrated components, network node 1460 and wirelessdevice (WD) 1410 are depicted with additional detail. The wirelessnetwork can provide communication and other types of services to one ormore wireless devices to facilitate the wireless devices' access toand/or use of the services provided by, or via, the wireless network.

The wireless network can comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork can be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network can implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 810.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network 1430 can comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 1460 and WD 1410 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network can comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that canfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node can refer to equipment capable, configured,arranged, and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network, thereby to facilitate, enable, and/or provide wirelessaccess to the wireless device and/or to perform other functions (e.g.,administration) in the wireless network. Examples of network nodesinclude, but are not limited to, access points (APs) (e.g., radio accesspoints), base stations (BSs) (e.g., radio base stations, Node Bs,evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations can becategorized based on the amount of coverage they provide (or, stateddifferently, their transmit power level) and can then also be referredto as femto base stations, pico base stations, micro base stations, ormacro base stations. A base station can be a relay node or a relay donornode controlling a relay. A network node can also include one or more(or all) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station can also be referred to as nodes in adistributed antenna system (DAS).

Further examples of network nodes include multi-standard radio (MSR)equipment such as MSR BSs, network controllers such as radio networkcontrollers (RNCs) or base station controllers (BSCs), base transceiverstations (BTSs), transmission points, transmission nodes,multi-cell/multicast coordination entities (MCEs), core network nodes(e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes(e.g., E-SMLCs), and/or MDTs. As another example, a network node can bea virtual network node as described in more detail below. Moregenerally, however, network nodes can represent any suitable device (orgroup of devices) capable, configured, arranged, and/or operable toenable and/or provide a wireless device with access to the wirelessnetwork or to provide some service to a wireless device that hasaccessed the wireless network.

In FIG. 14, network node 1460 includes processing circuitry 1470, devicereadable medium 1480, interface 1490, auxiliary equipment 1484, powersource 1486, power circuitry 1487, and antenna 1462. Although networknode 1460 illustrated in the example wireless network of FIG. 14 canrepresent a device that includes the illustrated combination of hardwarecomponents, other embodiments can comprise network nodes with differentcombinations of components. It is to be understood that a network nodecomprises any suitable combination of hardware and/or software needed toperform the tasks, features, functions and methods and/or proceduresdisclosed herein. Moreover, while the components of network node 1460are depicted as single boxes located within a larger box, or nestedwithin multiple boxes, in practice, a network node can comprise multipledifferent physical components that make up a single illustratedcomponent (e.g., device readable medium 1480 can comprise multipleseparate hard drives as well as multiple RAM modules).

Similarly, network node 1460 can be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which can each have their ownrespective components. In certain scenarios in which network node 1460comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components can be shared among severalnetwork nodes. For example, a single RNC can control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, can in someinstances be considered a single separate network node. In someembodiments, network node 1460 can be configured to support multipleradio access technologies (RATs). In such embodiments, some componentscan be duplicated (e.g., separate device readable medium 1480 for thedifferent RATs) and some components can be reused (e.g., the sameantenna 1462 can be shared by the RATs). Network node 1460 can alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 1460, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies can be integrated into thesame or different chip or set of chips and other components withinnetwork node 1460.

Processing circuitry 1470 can be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 1470 can include processinginformation obtained by processing circuitry 1470 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry 1470 can comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 1460 components, such as device readable medium 1480, network node1460 functionality. For example, processing circuitry 1470 can executeinstructions stored in device readable medium 1480 or in memory withinprocessing circuitry 1470. Such functionality can include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 1470 can include asystem on a chip (SOC).

In some embodiments, processing circuitry 1470 can include one or moreof radio frequency (RF) transceiver circuitry 1472 and basebandprocessing circuitry 1474. In some embodiments, radio frequency (RF)transceiver circuitry 1472 and baseband processing circuitry 1474 can beon separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry 1472 and baseband processing circuitry 1474 can beon the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device can be performed by processing circuitry 1470executing instructions stored on device readable medium 1480 or memorywithin processing circuitry 1470. In alternative embodiments, some orall of the functionality can be provided by processing circuitry 1470without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry 1470 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry 1470 alone or toother components of network node 1460, but are enjoyed by network node1460 as a whole, and/or by end users and the wireless network generally.

Device readable medium 1480 can comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that can be used byprocessing circuitry 1470. Device readable medium 1480 can store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 1470 and, utilized by network node 1460. Devicereadable medium 1480 can be used to store any calculations made byprocessing circuitry 1470 and/or any data received via interface 1490.In some embodiments, processing circuitry 1470 and device readablemedium 1480 can be considered to be integrated.

Interface 1490 is used in the wired or wireless communication ofsignalling and/or data between network node 1460, network 1430, and/orWDs 1410. As illustrated, interface 1490 comprises port(s)/terminal(s)1494 to send and receive data, for example to and from network 1430 overa wired connection. Interface 1490 also includes radio front endcircuitry 1492 that can be coupled to, or in certain embodiments a partof, antenna 1462. Radio front end circuitry 1492 comprises filters 1498and amplifiers 1496. Radio front end circuitry 1492 can be connected toantenna 1462 and processing circuitry 1470. Radio front end circuitrycan be configured to condition signals communicated between antenna 1462and processing circuitry 1470. Radio front end circuitry 1492 canreceive digital data that is to be sent out to other network nodes orWDs via a wireless connection. Radio front end circuitry 1492 canconvert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 1498and/or amplifiers 1496. The radio signal can then be transmitted viaantenna 1462. Similarly, when receiving data, antenna 1462 can collectradio signals which are then converted into digital data by radio frontend circuitry 1492. The digital data can be passed to processingcircuitry 1470. In other embodiments, the interface can comprisedifferent components and/or different combinations of components.

In certain alternative embodiments, network node 1460 may not includeseparate radio front end circuitry 1492, instead, processing circuitry1470 can comprise radio front end circuitry and can be connected toantenna 1462 without separate radio front end circuitry 1492. Similarly,in some embodiments, all or some of RF transceiver circuitry 1472 can beconsidered a part of interface 1490. In still other embodiments,interface 1490 can include one or more ports or terminals 1494, radiofront end circuitry 1492, and RF transceiver circuitry 1472, as part ofa radio unit (not shown), and interface 1490 can communicate withbaseband processing circuitry 1474, which is part of a digital unit (notshown).

Antenna 1462 can include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 1462 can becoupled to radio front end circuitry 1490 and can be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 1462 can comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna can be used to transmit/receive radio signalsin any direction, a sector antenna can be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna canbe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna can be referred to as MIMO. In certain embodiments, antenna 1462can be separate from network node 1460 and can be connectable to networknode 1460 through an interface or port.

Antenna 1462, interface 1490, and/or processing circuitry 1470 can beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals can be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 1462, interface 1490, and/or processing circuitry 1470 can beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalscan be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 1487 can comprise, or be coupled to, power managementcircuitry and can be configured to supply the components of network node1460 with power for performing the functionality described herein. Powercircuitry 1487 can receive power from power source 1486. Power source1486 and/or power circuitry 1487 can be configured to provide power tothe various components of network node 1460 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 1486 can either be included in,or external to, power circuitry 1487 and/or network node 1460. Forexample, network node 1460 can be connectable to an external powersource (e.g., an electricity outlet) via an input circuitry or interfacesuch as an electrical cable, whereby the external power source suppliespower to power circuitry 1487. As a further example, power source 1486can comprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 1487. Thebattery can provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, can also beused.

Alternative embodiments of network node 1460 can include additionalcomponents beyond those shown in FIG. 14 that can be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 1460 can include user interface equipment to allow and/orfacilitate input of information into network node 1460 and to allowand/or facilitate output of information from network node 1460. This canallow and/or facilitate a user to perform diagnostic, maintenance,repair, and other administrative functions for network node 1460.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD can be used interchangeably herein with user equipment (UE).Communicating wirelessly can involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD can be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD can be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc.

A WD can support device-to-device (D2D) communication, for example byimplementing a 3GPP standard for sidelink communication,vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I),vehicle-to-everything (V2X) and can in this case be referred to as a D2Dcommunication device. As yet another specific example, in an Internet ofThings (IoT) scenario, a WD can represent a machine or other device thatperforms monitoring and/or measurements, and transmits the results ofsuch monitoring and/or measurements to another WD and/or a network node.The WD can in this case be a machine-to-machine (M2M) device, which canin a 3GPP context be referred to as an MTC device. As one particularexample, the WD can be a UE implementing the 3GPP narrow band internetof things (NB-IoT) standard. Particular examples of such machines ordevices are sensors, metering devices such as power meters, industrialmachinery, or home or personal appliances (e.g. refrigerators,televisions, etc.) personal wearables (e.g., watches, fitness trackers,etc.). In other scenarios, a WD can represent a vehicle or otherequipment that is capable of monitoring and/or reporting on itsoperational status or other functions associated with its operation. AWD as described above can represent the endpoint of a wirelessconnection, in which case the device can be referred to as a wirelessterminal. Furthermore, a WD as described above can be mobile, in whichcase it can also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 1410 includes antenna 1411, interface1414, processing circuitry 1420, device readable medium 1430, userinterface equipment 1432, auxiliary equipment 1434, power source 1436and power circuitry 1437. WD 1410 can include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD 1410, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies can be integrated into the same or different chipsor set of chips as other components within WD 1410.

Antenna 1411 can include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 1414. In certain alternative embodiments, antenna 1411 can beseparate from WD 1410 and be connectable to WD 1410 through an interfaceor port. Antenna 1411, interface 1414, and/or processing circuitry 1420can be configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals can be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 1411 can beconsidered an interface.

As illustrated, interface 1414 comprises radio front end circuitry 1412and antenna 1411. Radio front end circuitry 1412 comprise one or morefilters 1418 and amplifiers 1416. Radio front end circuitry 1414 isconnected to antenna 1411 and processing circuitry 1420, and can beconfigured to condition signals communicated between antenna 1411 andprocessing circuitry 1420. Radio front end circuitry 1412 can be coupledto or a part of antenna 1411. In some embodiments, WD 1410 may notinclude separate radio front end circuitry 1412; rather, processingcircuitry 1420 can comprise radio front end circuitry and can beconnected to antenna 1411. Similarly, in some embodiments, some or allof RF transceiver circuitry 1422 can be considered a part of interface1414. Radio front end circuitry 1412 can receive digital data that is tobe sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry 1412 can convert the digital data into a radiosignal having the appropriate channel and bandwidth parameters using acombination of filters 1418 and/or amplifiers 1416. The radio signal canthen be transmitted via antenna 1411. Similarly, when receiving data,antenna 1411 can collect radio signals which are then converted intodigital data by radio front end circuitry 1412. The digital data can bepassed to processing circuitry 1420. In other embodiments, the interfacecan comprise different components and/or different combinations ofcomponents.

Processing circuitry 1420 can comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 1410components, such as device readable medium 1430, WD 1410 functionality.Such functionality can include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry1420 can execute instructions stored in device readable medium 1430 orin memory within processing circuitry 1420 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 1420 includes one or more of RFtransceiver circuitry 1422, baseband processing circuitry 1424, andapplication processing circuitry 1426. In other embodiments, theprocessing circuitry can comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry1420 of WD 1410 can comprise a SOC. In some embodiments, RF transceivercircuitry 1422, baseband processing circuitry 1424, and applicationprocessing circuitry 1426 can be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry1424 and application processing circuitry 1426 can be combined into onechip or set of chips, and RF transceiver circuitry 1422 can be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 1422 and baseband processing circuitry1424 can be on the same chip or set of chips, and application processingcircuitry 1426 can be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 1422,baseband processing circuitry 1424, and application processing circuitry1426 can be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 1422 can be a part of interface1414. RF transceiver circuitry 1422 can condition RF signals forprocessing circuitry 1420.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD can be provided by processingcircuitry 1420 executing instructions stored on device readable medium1430, which in certain embodiments can be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality canbe provided by processing circuitry 1420 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 1420 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 1420 alone or to other components ofWD 1410, but are enjoyed by WD 1410 as a whole, and/or by end users andthe wireless network generally.

Processing circuitry 1420 can be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 1420, can include processinginformation obtained by processing circuitry 1420 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 1410, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 1430 can be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 1420. Device readable medium 1430 can includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that can be used by processing circuitry 1420. In someembodiments, processing circuitry 1420 and device readable medium 1430can be considered to be integrated.

User interface equipment 1432 can include components that allow and/orfacilitate a human user to interact with WD 1410. Such interaction canbe of many forms, such as visual, audial, tactile, etc. User interfaceequipment 1432 can be operable to produce output to the user and toallow and/or facilitate the user to provide input to WD 1410. The typeof interaction can vary depending on the type of user interfaceequipment 1432 installed in WD 1410. For example, if WD 1410 is a smartphone, the interaction can be via a touch screen; if WD 1410 is a smartmeter, the interaction can be through a screen that provides usage(e.g., the number of gallons used) or a speaker that provides an audiblealert (e.g., if smoke is detected). User interface equipment 1432 caninclude input interfaces, devices and circuits, and output interfaces,devices and circuits. User interface equipment 1432 can be configured toallow and/or facilitate input of information into WD 1410, and isconnected to processing circuitry 1420 to allow and/or facilitateprocessing circuitry 1420 to process the input information. Userinterface equipment 1432 can include, for example, a microphone, aproximity or other sensor, keys/buttons, a touch display, one or morecameras, a USB port, or other input circuitry. User interface equipment1432 is also configured to allow and/or facilitate output of informationfrom WD 1410, and to allow and/or facilitate processing circuitry 1420to output information from WD 1410. User interface equipment 1432 caninclude, for example, a speaker, a display, vibrating circuitry, a USBport, a headphone interface, or other output circuitry. Using one ormore input and output interfaces, devices, and circuits, of userinterface equipment 1432, WD 1410 can communicate with end users and/orthe wireless network, and allow and/or facilitate them to benefit fromthe functionality described herein.

Auxiliary equipment 1434 is operable to provide more specificfunctionality which may not be generally performed by WDs. This cancomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 1434 can vary depending on the embodiment and/or scenario.

Power source 1436 can, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, can also be used. WD 1410 can further comprise power circuitry1437 for delivering power from power source 1436 to the various parts ofWD 1410 which need power from power source 1436 to carry out anyfunctionality described or indicated herein. Power circuitry 1437 can incertain embodiments comprise power management circuitry. Power circuitry1437 can additionally or alternatively be operable to receive power froman external power source; in which case WD 1410 can be connectable tothe external power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 1437 can also in certain embodiments be operable to deliverpower from an external power source to power source 1436. This can be,for example, for the charging of power source 1436. Power circuitry 1437can perform any converting or other modification to the power from powersource 1436 to make it suitable for supply to the respective componentsof WD 1410.

FIG. 15 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE can represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE canrepresent a device that is not intended for sale to, or operation by, anend user but which can be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE 15200 can be any UE identified bythe 3^(rd) Generation Partnership Project (3GPP), including a NB-IoT UE,a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE 1500, as illustrated in FIG. 15, is one example of a WD configuredfor communication in accordance with one or more communication standardspromulgated by the 3^(rd) Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE can be used interchangeable. Accordingly, although FIG.15 is a UE, the components discussed herein are equally applicable to aWD, and vice-versa.

In FIG. 15, UE 1500 includes processing circuitry 1501 that isoperatively coupled to input/output interface 1505, radio frequency (RF)interface 1509, network connection interface 1511, memory 1515 includingrandom access memory (RAM) 1517, read-only memory (ROM) 1519, andstorage medium 1521 or the like, communication subsystem 1531, powersource 1533, and/or any other component, or any combination thereof.Storage medium 1521 includes operating system 1523, application program1525, and data 1527. In other embodiments, storage medium 1521 caninclude other similar types of information. Certain UEs can utilize allof the components shown in FIG. 15, or only a subset of the components.The level of integration between the components can vary from one UE toanother UE. Further, certain UEs can contain multiple instances of acomponent, such as multiple processors, memories, transceivers,transmitters, receivers, etc.

In FIG. 15, processing circuitry 1501 can be configured to processcomputer instructions and data. Processing circuitry 1501 can beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 1501 can include twocentral processing units (CPUs). Data can be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 1505 can beconfigured to provide a communication interface to an input device,output device, or input and output device. UE 1500 can be configured touse an output device via input/output interface 1505. An output devicecan use the same type of interface port as an input device. For example,a USB port can be used to provide input to and output from UE 1500. Theoutput device can be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE 1500 can be configured to use aninput device via input/output interface 1505 to allow and/or facilitatea user to capture information into UE 1500. The input device can includea touch-sensitive or presence-sensitive display, a camera (e.g., adigital camera, a digital video camera, a web camera, etc.), amicrophone, a sensor, a mouse, a trackball, a directional pad, atrackpad, a scroll wheel, a smartcard, and the like. Thepresence-sensitive display can include a capacitive or resistive touchsensor to sense input from a user. A sensor can be, for instance, anaccelerometer, a gyroscope, a tilt sensor, a force sensor, amagnetometer, an optical sensor, a proximity sensor, another likesensor, or any combination thereof. For example, the input device can bean accelerometer, a magnetometer, a digital camera, a microphone, and anoptical sensor.

In FIG. 15, RF interface 1509 can be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface 1511 can beconfigured to provide a communication interface to network 1543 a.Network 1543 a can encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network 1543 a can comprise aWi-Fi network. Network connection interface 1511 can be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface 1511 can implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions can share circuit components, software or firmware,or alternatively can be implemented separately.

RAM 1517 can be configured to interface via bus 1510 to processingcircuitry 1501 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 1519 canbe configured to provide computer instructions or data to processingcircuitry 1501. For example, ROM 1519 can be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage medium1521 can be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 1521 can be configured toinclude operating system 1523, application program 1525 such as a webbrowser application, a widget or gadget engine or another application,and data file 1527. Storage medium 1521 can store, for use by UE 1500,any of a variety of various operating systems or combinations ofoperating systems.

Storage medium 1521 can be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 1521 can allow and/or facilitate UE 1500 to accesscomputer-executable instructions, application programs or the like,stored on transitory or non-transitory memory media, to off-load data,or to upload data. An article of manufacture, such as one utilizing acommunication system can be tangibly embodied in storage medium 1521,which can comprise a device readable medium.

In FIG. 15, processing circuitry 1501 can be configured to communicatewith network 1543 b using communication subsystem 1531. Network 1543 aand network 1543 b can be the same network or networks or differentnetwork or networks. Communication subsystem 1531 can be configured toinclude one or more transceivers used to communicate with network 1543b. For example, communication subsystem 1531 can be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 810.15,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver caninclude transmitter 1533 and/or receiver 1535 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 1533and receiver 1535 of each transceiver can share circuit components,software or firmware, or alternatively can be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 1531 can include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 1531 can include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 1543 b can encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network1543 b can be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 1513 can be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 1500. Asanother example, one of networks 1543 a-b can be an LTE RAN and theother of networks 1543 a-b can be an NR RAN.

The features, benefits and/or functions described herein can beimplemented in one of the components of UE 1500 or partitioned acrossmultiple components of UE 1500. Further, the features, benefits, and/orfunctions described herein can be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem1531 can be configured to include any of the components describedherein. Further, processing circuitry 1501 can be configured tocommunicate with any of such components over bus 1510. In anotherexample, any of such components can be represented by programinstructions stored in memory that when executed by processing circuitry1501 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components can be partitionedbetween processing circuitry 1501 and communication subsystem 1531. Inanother example, the non-computationally intensive functions of any ofsuch components can be implemented in software or firmware and thecomputationally intensive functions can be implemented in hardware.

FIG. 16 is a schematic block diagram illustrating a virtualizationenvironment 1600 in which functions implemented by some embodiments canbe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which can includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein canbe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 1600 hosted byone or more of hardware nodes 1630. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node can beentirely virtualized.

The functions can be implemented by one or more applications 1620 (whichcan alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 1620 are runin virtualization environment 1600 which provides hardware 1630comprising processing circuitry 1660 and memory 1690. Memory 1690contains instructions 1695 executable by processing circuitry 1660whereby application 1620 is operative to provide one or more of thefeatures, benefits, and/or functions disclosed herein.

Virtualization environment 1600, comprises general-purpose orspecial-purpose network hardware devices 1630 comprising a set of one ormore processors or processing circuitry 1660, which can be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device can comprise memory 1690-1 which can benon-persistent memory for temporarily storing instructions 1695 orsoftware executed by processing circuitry 1660. Each hardware device cancomprise one or more network interface controllers (NICs) 1670, alsoknown as network interface cards, which include physical networkinterface 1680. Each hardware device can also include non-transitory,persistent, machine-readable storage media 1690-2 having stored thereinsoftware 1695 and/or instructions executable by processing circuitry1660. Software 1695 can include any type of software including softwarefor instantiating one or more virtualization layers 1650 (also referredto as hypervisors), software to execute virtual machines 1640 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 1640, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and can be run by acorresponding virtualization layer 1650 or hypervisor. Differentembodiments of the instance of virtual appliance 1620 can be implementedon one or more of virtual machines 1640, and the implementations can bemade in different ways.

During operation, processing circuitry 1660 executes software 1695 toinstantiate the hypervisor or virtualization layer 1650, which cansometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 1650 can present a virtual operating platform thatappears like networking hardware to virtual machine 1640.

As shown in FIG. 16, hardware 1630 can be a standalone network node withgeneric or specific components. Hardware 1630 can comprise antenna 16225and can implement some functions via virtualization. Alternatively,hardware 1630 can be part of a larger cluster of hardware (e.g. such asin a data center or customer premise equipment (CPE)) where manyhardware nodes work together and are managed via management andorchestration (MANO) 16100, which, among others, oversees lifecyclemanagement of applications 1620.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV can be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 1640 can be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 1640, and that part of hardware 1630 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 1640, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 1640 on top of hardware networking infrastructure1630 and corresponds to application 1620 in FIG. 16.

In some embodiments, one or more radio units 16200 that each include oneor more transmitters 16220 and one or more receivers 16210 can becoupled to one or more antennas 16225. Radio units 16200 can communicatedirectly with hardware nodes 1630 via one or more appropriate networkinterfaces and can be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio accessnode or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system 16230 which can alternatively be used for communicationbetween the hardware nodes 1630 and radio units 16200.

With reference to FIG. 17, in accordance with an embodiment, acommunication system includes telecommunication network 1710, such as a3GPP-type cellular network, which comprises access network 1711, such asa radio access network, and core network 1714. Access network 1711comprises a plurality of base stations 1712 a, 1712 b, 1712 c, such asNBs, eNBs, gNBs or other types of wireless access points, each defininga corresponding coverage area 1713 a, 1713 b, 1713 c. Each base station1712 a, 1712 b, 1712 c is connectable to core network 1714 over a wiredor wireless connection 1715. A first UE 1791 located in coverage area1713 c can be configured to wirelessly connect to, or be paged by, thecorresponding base station 1712 c. A second UE 1792 in coverage area1713 a is wirelessly connectable to the corresponding base station 1712a. While a plurality of UEs 1791, 1792 are illustrated in this example,the disclosed embodiments are equally applicable to a situation where asole UE is in the coverage area or where a sole UE is connecting to thecorresponding base station 1712.

Telecommunication network 1710 is itself connected to host computer1730, which can be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer 1730 can beunder the ownership or control of a service provider, or can be operatedby the service provider or on behalf of the service provider.Connections 1721 and 1722 between telecommunication network 1710 andhost computer 1730 can extend directly from core network 1714 to hostcomputer 1730 or can go via an optional intermediate network 1720.Intermediate network 1720 can be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network 1720,if any, can be a backbone network or the Internet; in particular,intermediate network 1720 can comprise two or more sub-networks (notshown).

The communication system of FIG. 17 as a whole enables connectivitybetween the connected UEs 1791, 1792 and host computer 1730. Theconnectivity can be described as an over-the-top (OTT) connection 1750.Host computer 1730 and the connected UEs 1791, 1792 are configured tocommunicate data and/or signaling via OTT connection 1750, using accessnetwork 1711, core network 1714, any intermediate network 1720 andpossible further infrastructure (not shown) as intermediaries. OTTconnection 1750 can be transparent in the sense that the participatingcommunication devices through which OTT connection 1750 passes areunaware of routing of uplink and downlink communications. For example,base station 1712 may not or need not be informed about the past routingof an incoming downlink communication with data originating from hostcomputer 1730 to be forwarded (e.g., handed over) to a connected UE1791. Similarly, base station 1712 need not be aware of the futurerouting of an outgoing uplink communication originating from the UE 1791towards the host computer 1730.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 18. In communication system1800, host computer 1810 comprises hardware 1815 including communicationinterface 1816 configured to set up and maintain a wired or wirelessconnection with an interface of a different communication device ofcommunication system 1800. Host computer 1810 further comprisesprocessing circuitry 1818, which can have storage and/or processingcapabilities. In particular, processing circuitry 1818 can comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. Host computer 1810 furthercomprises software 1811, which is stored in or accessible by hostcomputer 1810 and executable by processing circuitry 1818. Software 1811includes host application 1812. Host application 1812 can be operable toprovide a service to a remote user, such as UE 1830 connecting via OTTconnection 1850 terminating at UE 1830 and host computer 1810. Inproviding the service to the remote user, host application 1812 canprovide user data which is transmitted using OTT connection 1850.

Communication system 1800 can also include base station 1820 provided ina telecommunication system and comprising hardware 1825 enabling it tocommunicate with host computer 1810 and with UE 1830. Hardware 1825 caninclude communication interface 1826 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 1800, as well as radiointerface 1827 for setting up and maintaining at least wirelessconnection 1870 with UE 1830 located in a coverage area (not shown inFIG. 18) served by base station 1820. Communication interface 1826 canbe configured to facilitate connection 1860 to host computer 1810.Connection 1860 can be direct or it can pass through a core network (notshown in FIG. 18) of the telecommunication system and/or through one ormore intermediate networks outside the telecommunication system. In theembodiment shown, hardware 1825 of base station 1820 can also includeprocessing circuitry 1828, which can comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 1820 further has software 1821 storedinternally or accessible via an external connection.

Communication system 1800 can also include UE 1830 already referred to.Its hardware 1835 can include radio interface 1837 configured to set upand maintain wireless connection 1870 with a base station serving acoverage area in which UE 1830 is currently located. Hardware 1835 of UE1830 can also include processing circuitry 1838, which can comprise oneor more programmable processors, application-specific integratedcircuits, field programmable gate arrays or combinations of these (notshown) adapted to execute instructions. UE 1830 further comprisessoftware 1831, which is stored in or accessible by UE 1830 andexecutable by processing circuitry 1838. Software 1831 includes clientapplication 1832. Client application 1832 can be operable to provide aservice to a human or non-human user via UE 1830, with the support ofhost computer 1810. In host computer 1810, an executing host application1812 can communicate with the executing client application 1832 via OTTconnection 1850 terminating at UE 1830 and host computer 1810. Inproviding the service to the user, client application 1832 can receiverequest data from host application 1812 and provide user data inresponse to the request data. OTT connection 1850 can transfer both therequest data and the user data. Client application 1832 can interactwith the user to generate the user data that it provides.

It is noted that host computer 1810, base station 1820 and UE 1830illustrated in FIG. 18 can be similar or identical to host computer1730, one of base stations 1712 a, 1712 b, 1712 c and one of UEs 1791,1792 of FIG. 17, respectively. This is to say, the inner workings ofthese entities can be as shown in FIG. 18 and independently, thesurrounding network topology can be that of FIG. 17.

In FIG. 18, OTT connection 1850 has been drawn abstractly to illustratethe communication between host computer 1810 and UE 1830 via basestation 1820, without explicit reference to any intermediary devices andthe precise routing of messages via these devices. Networkinfrastructure can determine the routing, which it can be configured tohide from UE 1830 or from the service provider operating host computer1810, or both. While OTT connection 1850 is active, the networkinfrastructure can further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection 1870 between UE 1830 and base station 1820 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 1830 using OTT connection1850, in which wireless connection 1870 forms the last segment. Moreprecisely, the exemplary embodiments disclosed herein can improveflexibility for the network to monitor end-to-end quality-of-service(QoS) of data flows, including their corresponding radio bearers,associated with data sessions between a user equipment (UE) and anotherentity, such as an OTT data application or service external to the 5Gnetwork. These and other advantages can facilitate more timely design,implementation, and deployment of 5G/NR solutions. Furthermore, suchembodiments can facilitate flexible and timely control of data sessionQoS, which can lead to improvements in capacity, throughput, latency,etc. that are envisioned by 5G/NR and important for the growth of OTTservices.

A measurement procedure can be provided for the purpose of monitoringdata rate, latency and other network operational aspects on which theone or more embodiments improve. There can further be an optionalnetwork functionality for reconfiguring OTT connection 1850 between hostcomputer 1810 and UE 1830, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring OTT connection 1850 can be implemented in software 1811and hardware 1815 of host computer 1810 or in software 1831 and hardware1835 of UE 1830, or both. In embodiments, sensors (not shown) can bedeployed in or in association with communication devices through whichOTT connection 1850 passes; the sensors can participate in themeasurement procedure by supplying values of the monitored quantitiesexemplified above, or supplying values of other physical quantities fromwhich software 1811, 1831 can compute or estimate the monitoredquantities. The reconfiguring of OTT connection 1850 can include messageformat, retransmission settings, preferred routing etc.; thereconfiguring need not affect base station 1820, and it can be unknownor imperceptible to base station 1820. Such procedures andfunctionalities can be known and practiced in the art. In certainembodiments, measurements can involve proprietary UE signalingfacilitating host computer 1810's measurements of throughput,propagation times, latency and the like. The measurements can beimplemented in that software 1811 and 1831 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 1850 while it monitors propagation times, errors etc.

FIG. 19 is a flowchart illustrating an exemplary method and/or procedureimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which, in some exemplary embodiments, can be thosedescribed with reference to FIGS. 17 and 18. For simplicity of thepresent disclosure, only drawing references to FIG. 19 will be includedin this section. In step 1910, the host computer provides user data. Insubstep 1911 (which can be optional) of step 1910, the host computerprovides the user data by executing a host application. In step 1920,the host computer initiates a transmission carrying the user data to theUE. In step 1930 (which can be optional), the base station transmits tothe UE the user data which was carried in the transmission that the hostcomputer initiated, in accordance with the teachings of the embodimentsdescribed throughout this disclosure. In step 1940 (which can also beoptional), the UE executes a client application associated with the hostapplication executed by the host computer.

FIG. 20 is a flowchart illustrating an exemplary method and/or procedureimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which can be those described with reference to FIGS. 17and 18. For simplicity of the present disclosure, only drawingreferences to FIG. 20 will be included in this section. In step 2010 ofthe method, the host computer provides user data. In an optional substep(not shown) the host computer provides the user data by executing a hostapplication. In step 2100, the host computer initiates a transmissioncarrying the user data to the UE. The transmission can pass via the basestation, in accordance with the teachings of the embodiments describedthroughout this disclosure. In step 2030 (which can be optional), the UEreceives the user data carried in the transmission.

FIG. 21 is a flowchart illustrating an exemplary method and/or procedureimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which can be those described with reference to FIGS. 17and 18. For simplicity of the present disclosure, only drawingreferences to FIG. 21 will be included in this section. In step 2110(which can be optional), the UE receives input data provided by the hostcomputer. Additionally or alternatively, in step 2120, the UE providesuser data. In substep 2121 (which can be optional) of step 2120, the UEprovides the user data by executing a client application. In substep2111 (which can be optional) of step 2110, the UE executes a clientapplication which provides the user data in reaction to the receivedinput data provided by the host computer. In providing the user data,the executed client application can further consider user input receivedfrom the user. Regardless of the specific manner in which the user datawas provided, the UE initiates, in substep 2130 (which can be optional),transmission of the user data to the host computer. In step 2140 of themethod, the host computer receives the user data transmitted from theUE, in accordance with the teachings of the embodiments describedthroughout this disclosure.

FIG. 22 is a flowchart illustrating an exemplary method and/or procedureimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which can be those described with reference to FIGS. 17and 18. For simplicity of the present disclosure, only drawingreferences to FIG. 22 will be included in this section. In step 2210(which can be optional), in accordance with the teachings of theembodiments described throughout this disclosure, the base stationreceives user data from the UE. In step 2220 (which can be optional),the base station initiates transmission of the received user data to thehost computer. In step 2230 (which can be optional), the host computerreceives the user data carried in the transmission initiated by the basestation.

The term unit can have conventional meaning in the field of electronics,electrical devices and/or electronic devices and can include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Exemplary embodiments of the present disclosure include the followingenumerated embodiments.

-   -   1. A method performed by a first network node in a first radio        access network (RAN), the first network node in communication        with a second network node in a second RAN, the method        comprising:        -   determining one or more group identifiers associated with at            least one of:            -   i. a user equipment (UE) served by the first network                node; and            -   ii. a subscriber associated with the UE;        -   sending a request for the second network node to establish            dual connectivity, as a secondary node (SN), with the UE,            wherein the request comprises information relating to the            one or more group identifiers; and        -   managing the UE's access to resources of the first RAN based            on the one or more group identifiers.    -   2. The method of embodiment 1, wherein the information relating        to the one or more group identifiers is usable by the second        network node to manage the UE's access to resources of the        second RAN.    -   3. The method of any of embodiments 1-2, wherein:        -   The first network node is an eNB in an LTE RAN; and        -   The second network node is a gNB in an NR RAN.    -   4. The method of any of embodiments 1-3, wherein the one or more        group identifiers comprise at least one of a Subscriber Profile        ID for RAT/Frequency Priority (SPID) and a Dedicated Core        Network ID (DCN-id).    -   5. The method of any of embodiments 1-4, wherein the information        relating to the SPID comprises a RAT/Frequency Selection        Priority (RFSP).    -   6. The method of any of embodiments 1-3, wherein the information        relating to the DCN-id comprises an index value that maps to one        or more policies for managing UE access to resources of the        second RAN.    -   7. The method of any of embodiments 1-3, wherein each of the one        or more group identifiers is determined based on one or more of        Subscribers Profile ID for RAT/Frequency Priority (SPID),        Dedicated Core Network ID (DCN-id), Public Land Mobile Network        ID (PLMN-id), QoS Class Indicator (QCI), and Closed Subscriber        Group (CSG) membership.    -   8. The method of any of embodiments 1-7, wherein managing the        UE's access to resources of the first RAN is further based on a        profile of the subscriber associated with the UE.    -   9. A method performed by a second network node in a second radio        access network (RAN), the second network node in communication        with a first network node in a first RAN, the method comprising:        -   receiving a request from the first network node to establish            dual connectivity, as a secondary node (SN), with a user            equipment (UE) served by the first network node, wherein the            request comprises information relating to one or more group            identifiers that are associated with at least one of:            -   i. the UE; and            -   ii. a subscriber associated with the UE;        -   managing the UE's access to resources of the second RAN            based on the one or more group identifiers.    -   10. The method of embodiment 9, wherein request is received by        central unit (CU) comprising the second network node, and the        method further comprises sending the information relating to the        one or more group identifiers to at least one distributed unit        (DU) comprising the second network node.    -   11. The method of any of embodiments 9-10, wherein:        -   The first network node is an eNB in an LTE RAN; and        -   The second network node is a gNB in an NR RAN.    -   12. The method of any of embodiments 9-11, wherein the one or        more group identifiers comprise at least one of a Subscriber        Profile ID for RAT/Frequency Priority (SPID) and a Dedicated        Core Network ID (DCN-id).    -   13. The method of any of embodiments 9-12, wherein the        information relating to the SPID comprises a RAT/Frequency        Selection Priority (RFSP).    -   14. The method of any of embodiments 9-12, wherein the        information relating to the DCN-id comprises an index value that        maps to one or more policies for managing UE access to resources        of the second RAN.    -   15. The method of any of embodiments 9-11, wherein each of the        one or more group identifiers is determined based on one or more        of Subscribers Profile ID for RAT/Frequency Priority (SPID),        Dedicated Core Network ID (DCN-id), Public Land Mobile Network        ID (PLMN-id), QoS Class Indicator (QCI), and Closed Subscriber        Group (CSG) membership.    -   16. The method of any of embodiments 9-15, wherein managing the        UE's access to resources of the second RAN is further based on a        profile of the subscriber associated with the UE.    -   17. The method of any of embodiments 9-15, wherein managing the        UE's access to resources of the second RAN is based on a policy        that prioritizes access by UEs associated with the one or more        group identifiers over access by UEs that are not associated        with all of the one or more identifiers.    -   18. The method of embodiment 17, wherein the policy prioritizes        access by UEs associated with the one or more group identifiers        to particular bandwidth part (BWP) frequency resources that are        allocated by the second RAN.    -   19. The method of any of embodiments 9-15, wherein managing the        UE's access to resources of the second RAN comprises        guaranteeing that UEs associated with the one or more group        identifiers can access at least a predefined proportion of        resources available in the second RAN.    -   20. A first network node in a first radio access network (RAN),        the first network node in communication with a second network        node in a second RAN, the first network node comprising:        -   processing circuitry configured to perform operations            corresponding to any of the methods of embodiments 1-8; and        -   power supply circuitry configured to supply power to the            first network node.    -   21. A second network node in a second radio access network        (RAN), the second network node in communication with a first        network node in a first RAN, the second network node comprising:        -   processing circuitry configured to perform operations            corresponding to any of the methods of embodiments 9-19; and        -   power supply circuitry configured to supply power to the            second network node.    -   22. A communication system including a host computer comprising:        -   processing circuitry configured to provide user data; and        -   a communication interface configured to forward the user            data to a cellular network for transmission to a user            equipment (UE),        -   wherein the cellular network comprises a first radio access            network (RAN) comprising a first network node and a second            RAN comprising a second network node, each of the first and            second network nodes having a radio interface and processing            circuitry;        -   the first network node's processing circuitry is configured            to perform operations corresponding to any of the methods of            embodiments 1-8; and        -   the second network node's processing circuitry is configured            to perform operations corresponding to any of the methods of            embodiments 9-19.    -   23. The communication system of embodiment 22, further including        a user equipment configured to communicate with at least one of        the first and second DUs.    -   24. The communication system of any of embodiments 22-23,        wherein:        -   the processing circuitry of the host computer is configured            to execute a host application, thereby providing the user            data; and        -   the UE comprises processing circuitry configured to execute            a client application associated with the host application.    -   25. A method implemented in a communication system including a        host computer, first and second network nodes, and a user        equipment (UE), the method comprising:        -   at the host computer, providing user data;        -   at the host computer, initiating a transmission carrying the            user data to the UE via a cellular network comprising the            first and second network nodes; and        -   operations, performed by the first network node,            corresponding to any of the methods of embodiments 1-8; and        -   operations, performed by the second network node,            corresponding to any of the methods of embodiments 9-19.    -   26. The method of embodiment 25, further comprising,        transmitting the user data by at least one of the first and        second network nodes.    -   27. The method of any of embodiments 25-26, wherein the user        data is provided at the host computer by executing a host        application, the method further comprising, at the UE, executing        a client application associated with the host application.    -   28. A communication system including a host computer comprising        a communication interface configured to receive user data        originating from a transmission from a user equipment (UE) to at        least one of a first network node comprising a first radio        access network (RAN) and a second network node comprising a        second RAN, wherein the second network node comprises a radio        interface and processing circuitry configured to perform        operations corresponding to any of the methods of embodiments        9-19, and wherein the first network node comprises processing        circuitry configured to perform operations corresponding to any        of the methods of embodiments 1-8.    -   29. The communication system of the previous embodiment further        including the first and second network nodes.    -   30. The communication system of any of embodiments 28-29,        further including the UE, wherein the UE is configured to        communicate with at least one of the first and second network        nodes.    -   31. The communication system of any of embodiments 28-30,        wherein:        -   the processing circuitry of the host computer is configured            to execute a host application;        -   the UE is configured to execute a client application            associated with the host application, thereby providing the            user data to be received by the host computer.

What is claimed is:
 1. A method performed by a first network node in aradio access network (RAN), the first network node being incommunication with a second network node configured with a differentradio access technology (RAT) than the first network node, wherein themethod comprises: determining one or more identifiers used for networkslicing in the RAT used by the first network node, wherein theidentifiers are associated with at least one of the following: a userequipment (UE) served by the first network node, a subscriber associatedwith the UE, and a group of UEs served by the first network node; andsending a request for the second network node to establish dualconnectivity, as a secondary node (SN) with the UE, wherein the requestcomprises information relating to the one or more identifiers, wherein:either a first set of conditions or a second set of conditions applies;the first set of conditions includes: the first network node is anevolved Node B (eNB) configured with a Long-Term Evolution (LTE) RAT,the second network node is a next-generation Node B (gNB) configuredwith a New Radio (NR) RAT, and the information relating to the one ormore group identifiers comprises a Subscriber Profile ID forRAT/Frequency Priority (SPID); and the second set of conditionsincludes: the first network node is a gNB configured with the NR RAT,the second network node is an eNB configured with the LTE RAT, and theinformation relating to the one or more identifiers comprises an indexto RAT/Frequency Selection Priority (RFSP).
 2. The method of claim 1,wherein the information relating to the one or more identifiers maps toone or more further network slicing policies for managing UE access toresources provided by a RAN that includes the second network node. 3.The method of claim 1, further comprising managing the UE's access toresources provided by the RAN based on one or more network slicingpolicies associated with the one or more identifiers.
 4. The method ofclaim 3, wherein the one or more network slicing policies are the sameas the one or more further network slicing policies.
 5. The method ofclaim 1, wherein each of the one or more identifiers is related to oneor more of the following: Subscribers Profile ID for RAT/FrequencyPriority (SPID); Dedicated Core Network ID (DCN-id); Public Land MobileNetwork ID (PLMN-id); Mobility Management Entity group identity (MMEGI);QoS Class Indicator (QCI); and Closed Subscriber Group (CSG) membership.6. A method performed by a second network node in a radio access network(RAN), the second network node being in communication with a firstnetwork node configured with a different radio access technology (RAT)than the second network node, wherein the method comprises: receiving arequest from the first network node to establish dual connectivity, as asecondary node (SN) with a user equipment (UE) served by the firstnetwork node, wherein the request comprises information relating to oneor more identifiers used for network slicing in the RAT used by thefirst network node, wherein the identifiers are associated with at leastone of the following: a user equipment (UE) served by the first networknode, a subscriber associated with the UE, and a group of UEs served bythe first network node; mapping the information relating to the one ormore identifiers to one or more network slicing policies in the RAT usedby the second network node, for managing the UE's access to resourcesprovided by the second network node; and managing the UE's access to theresources in accordance with the one or more policies, wherein: either afirst set of conditions or a second set of conditions applies; the firstset of conditions includes: the first network node is an evolved Node B(eNB) configured with a Long-Term Evolution (LTE) RAT, the secondnetwork node is a next-generation Node B (gNB) configured with a NewRadio (NR) RAT, and the information relating to the one or more groupidentifiers comprises a Subscriber Profile ID for RAT/Frequency Priority(SPID); and the second set of conditions includes: the first networknode is a gNB configured with the NR RAT, the second network node is aneNB configured with the LTE RAT, and the information relating to the oneor more identifiers comprises an index to RAT/Frequency SelectionPriority (RFSP).
 7. The method of claim 6, wherein the one or moreidentifiers maps to one or more further network slicing policies formanaging UE access to resources provided by a RAN that includes thefirst network node.
 8. The method of claim 7, wherein the one or morenetwork slicing policies are the same as the one or more further networkslicing policies.
 9. The method of claim 6, wherein at least one of thenetwork slicing policies prioritizes access by UEs associated with theone or more identifiers over access by UEs that are not associated withall of the one or more identifiers.
 10. The method of claim 9, whereinthe at least one policy network slicing prioritizes access by UEsassociated with the one or more identifiers to particular bandwidth part(BWP) frequency resources that are allocated by the second network node.11. The method of claim 6, wherein at least one of the network slicingpolicies guarantees that UEs associated with the one or more identifierscan access at least a predefined proportion of resources available fromthe RAN.
 12. A first network node in a radio access network (RAN), thefirst network node being arranged to communicate with a second networknode having a different radio access technology (RAT) than the firstnetwork node, wherein the first network node comprises: power supplycircuitry configured to supply power to the first network node; radiointerface circuitry configured to communicate with one or more userequipment (UEs); and processing circuitry operably coupled to the radiointerface circuitry and configured to: determine one or more identifiersused for network slicing in the RAT used by the first network node,wherein the identifiers are associated with at least one of thefollowing: a user equipment (UE) served by the first network node; asubscriber associated with the UE; and a group of UEs served by thefirst network node; and send a request for the second network node toestablish dual connectivity, as a secondary node (SN) with the UE,wherein the request comprises information relating to the one or moreidentifiers, wherein: either a first set of conditions or a second setof conditions applies; the first set of conditions includes: the firstnetwork node is an evolved Node B (eNB) configured with a Long-TermEvolution (LTE) RAT, the second network node is a next-generation Node B(gNB) configured with a New Radio (NR) RAT, and the information relatingto the one or more group identifiers comprises a Subscriber Profile IDfor RAT/Frequency Priority (SPID); and the second set of conditionsincludes: the first network node is a gNB configured with the NR RAT,the second network node is an eNB configured with the LTE RAT, and theinformation relating to the one or more identifiers comprises an indexto RAT/Frequency Selection Priority (RFSP).
 13. The first network nodeof claim 12, wherein the information relating to the one or moreidentifiers maps to one or more further network slicing policies formanaging UE access to resources provided by a RAN that includes thesecond network node.
 14. The first network node of claim 12, wherein theprocessing circuitry is further configured to manage the UE's access toresources provided by the RAN based on one or more network slicingpolicies associated with the one or more identifiers.
 15. The firstnetwork node of claim 14, wherein the one or more network slicingpolicies are the same as the one or more further network slicingpolicies.
 16. The first network node of claim 12, wherein each of theone or more identifiers is related to one or more of the following:Subscribers Profile ID for RAT/Frequency Priority (SPID); Dedicated CoreNetwork ID (DCN-id); Public Land Mobile Network ID (PLMN-id); MobilityManagement Entity group identity (MMEGI); QoS Class Indicator (QCI); andClosed Subscriber Group (CSG) membership.
 17. A second network node in aradio access network (RAN), the second network node being arranged tocommunicate with a first network node having a different radio accesstechnology (RAT) than the second network node, wherein the secondnetwork node comprises: power supply circuitry configured to supplypower to the second network node; radio interface circuitry configuredto communicate with one or more user equipment (UEs); and processingcircuitry operably coupled to the radio interface circuitry andconfigured to: receive a request from the first network node toestablish dual connectivity, as a secondary node (SN) with a userequipment (UE) served by the first network node, wherein the requestcomprises information relating to one or more identifiers used fornetwork slicing in the RAT used by the first network node, wherein theidentifiers are associated with at least one of the following: a userequipment (UE) served by the first network node; a subscriber associatedwith the UE; and a group of UEs served by the first network node; mapthe information relating to the one or more identifiers to one or morenetwork slicing policies in the RAT used by the second network node, formanaging the UE's access to resources provided by the second networknode; and manage the UE's access to the resources in accordance with theone or more policies wherein: either a first set of conditions or asecond set of conditions applies; the first set of conditions includes:the first network node is an evolved Node B (eNB) configured with aLong-Term Evolution (LTE) RAT, the second network node is anext-generation Node B (gNB) configured with a New Radio (NR) RAT, andthe information relating to the one or more group identifiers comprisesa Subscriber Profile ID for RAT/Frequency Priority (SPID); and thesecond set of conditions includes: the first network node is a gNBconfigured with the NR RAT, the second network node is an eNB configuredwith the LTE RAT, and the information relating to the one or moreidentifiers comprises an index to RAT/Frequency Selection Priority(RFSP).
 18. The second network node of claim 17, wherein the one or moreidentifiers map to one or more further network slicing policies formanaging UE access to resources provided by a RAN that includes thefirst network node.
 19. The second network node of claim 18, wherein theone or more network slicing policies are the same as the one or morefurther network slicing policies.
 20. The second network node of claim17, wherein at least one of the network slicing policies prioritizesaccess by UEs associated with the one or more identifiers over access byUEs that are not associated with all of the one or more identifiers. 21.The second network node of claim 20, wherein the at least one networkslicing policy prioritizes access by UEs associated with the one or moreidentifiers to particular bandwidth part (BWP) frequency resources thatare allocated by the second network node.
 22. The second network node ofclaim 17, wherein at least one of the network slicing policiesguarantees that UEs associated with the one or more identifiers canaccess at least a predefined proportion of resources available from theRAN.
 23. A non-transitory, computer-readable medium storingcomputer-executable instructions that, when executed by processingcircuitry comprising a network node, configure the network node toperform operations corresponding to the method of claim
 1. 24. Anon-transitory, computer-readable medium storing computer-executableinstructions that, when executed by processing circuitry comprising anetwork node, configure the network node to perform operationscorresponding to the method of claim 6.